This hot fix supplies support for the following new features in SAS/ACCESS Interface to Amazon Redshift:

• IAM role authentication for bulk-load and bulk-unload functionality. More specifically, when you use this feature, the COPY command (for BULKLOAD=YES) and the UNLOAD command (for BULKUNLOAD=YES) use IAM role authentication instead of key-based access control. This feature is available with the BL_IAM_ROLE data set option or its alias of BL_ROLE. Here is an example with the new option highlighted with bold text:
  data new;
  set redshift.table (BULKUNLOAD=YES BL_IAM_ROLE='1234567890:role/RedshiftRole');
  run;

Note: The IAM role is used only in the COPY or UNLOAD command that SAS/ACCESS Interface to Amazon Redshift generates. Valid credentials (including at least an access key ID and secret access key) must be available so that SAS/ACCESS Interface to Amazon Redshift can upload or download the data files to and from Amazon S3. You can provide these credentials either through the BL_KEY or BL_SECRET engine options or by configuring the AWS credentials file in the user's home directory under the .aws subdirectory.

• Server-side encryption for bulk-load and bulk-unload functionality. This option is available with the BL_ENCKEY= option. With this option, you can specify an AWS KMS encryption key that has been registered with the S3 procedure. This key can be created in the AWS console under the IAM service. The example below shows how to register and use the KMS key.
  proc s3 region=useast;
  enckey add name="my_key" id="12345678-90ab-cdef-1234-567890abcdef";
  run;
• Bulk-unload functionality. When you use bulk unload, the UNLOAD command is used to rapidly retrieve a large number of rows from the database. This feature is available with the BULKUNLOAD=YES option.
• Ability to define the number of threads used during bulk-unload processing. This feature is available with the BL_NUM_READ_THREADS option​​​​​​. When you use this option, you can set it from 1 to 10 with a default value of 4 and you can adjust it to optimize unloading based on the specific environment resources. Here is an example with the new option highlighted with bold text:
  data new;
  set redshift.table (BULKUNLOAD=YES BL_NUM_READ_THREADS=5);
  run;

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to Amazon Redshift 9.42 is available at: